-
Notifications
You must be signed in to change notification settings - Fork 27
Multi Relay Communication with Coordinator #118
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
| Ok((session.into(), connection_id_hex)) | ||
| } | ||
|
|
||
| /// Default DNS resolution logic that filters results by address family. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Cool - this appears to accomplish the same things I did in this PR: #111
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes. Sorry I noticed this later after doing the PR. But yeah this now covers for dns resolution by considering address family. Also I am planning to pass custom dns resolution logic in a seperate PR later.
…le implementation
This PR adds support for multi relay communication to have multiple relay's deployed and communicate about the namespaces for publishing and subscribing.
We now have a Coordinator interface which can be implemented based on user's requirement. There is already a file coordinator which uses file as a backend to store the information about the namespaces and relay url.